Funding a radio frequency device transaction

ABSTRACT

A transponder-reader payment system includes an RFID reader for interrogating a transponder and an RFID transponder device. The RFID reader receives, from the RFID transponder device, a code that is associated with a first funding source and a second funding source. The RFID reader communicates a request associated with a transaction to a payment processor. The request includes the code and the transaction is funded using the first funding source and the second funding source associated with the code. In one embodiment, the transaction is funded according to a funding account protocol associated with the code.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 12/337,287, filed Dec. 17, 2008, which is a continuation ofU.S. patent application Swe. No. 10/876,822, filed Jun. 24, 2004, nowU.S. Pat. No. 7,639,116, issued on Dec. 29, 2005, which is acontinuation of U.S. patent application Ser. No. 10/318,480, filed Dec.13, 2002, now U.S. Pat. No. 7,249,112, issued on Jul. 24, 2007, whichclaims priority to provisional U.S. patent application No. 60/396,577,filed Jul. 16, 2002. U.S. patent application Ser. No. 10/876,822 is alsoa continuation-in-part of U.S. patent application Ser. No. 10/192,488,filed Jul. 9, 2002, now U.S. Pat. No. 7,239,226, issued on Jul. 3, 2007,which claims priority to provisional U.S. patent application No.60/304,216, filed Jul. 10, 2001. All of the above applications areincorporated herein by reference.

FIELD OF INVENTION

This invention generally relates to facilitating a radio frequencydevice transaction, and more particularly, to facilitating a financialtransaction using a first funding source and a second funding source.

BACKGROUND OF THE INVENTION

Like barcode and voice data entry, RFID is a contactless informationacquisition technology. RFID systems are wireless, and are usuallyextremely effective in hostile environments where conventionalacquisition methods fail. RFID has established itself in a wide range ofmarkets, such as, for example, the high-speed reading of railwaycontainers, tracking moving objects such as livestock or automobiles,and retail inventory applications. As such, RFID technology has become aprimary focus in automated data collection, identification and analysissystems worldwide.

Of late, companies are increasingly embodying RFID data acquisitiontechnology in a fob or tag for use in completing financial transactions.A typical fob includes a transponder and is ordinarily a self-containeddevice which may be contained on any portable form factor. In someinstances, a battery may be included with the fob to power thetransponder. In which case the internal circuitry of the fob (includingthe transponder) may draw its operating power from the battery powersource. Alternatively, the fob may exist independently of an internalpower source. In this instance the internal circuitry of the fob(including the transponder) may gain its operating power directly froman RF interrogation signal. U.S. Pat. No. 5,053,774 issued to Schuermanndescribes a typical transponder RF interrogation system which may befound in the prior art. The Schuermann patent describes in general thepowering technology surrounding conventional transponder structures.U.S. Pat. No. 4,739,328 discusses a method by which a conventionaltransponder may respond to a RF interrogation signal. Other typicalmodulation techniques which may be used include, for example, ISO/IEC14443 and the like.

In the conventional fob powering technologies used, the fob is typicallyactivated upon presenting the fob in an interrogation signal. In thisregard, the fob may be activated irrespective of whether the userdesires such activation. Inadvertent presentation of the fob may resultin initiation and completion of an unwanted transaction. Thus, a fobsystem is needed which allows the fob user to control activation of thefob to limit transactions being undesirably completed.

One of the more visible uses of the RFID technology is found in theintroduction of Exxon/Mobil's Speedpass® and Shell's EasyPay® products.These products use transponders placed in a fob or tag which enablesautomatic identification of the user when the fob is presented at aPoint of Sale (POS) device. Fob identification data is typically passedto a third party server database, where the identification data isreferenced to a customer (e.g., user) credit or debit account. In anexemplary processing method, the server seeks authorization for thetransaction by passing the transaction and account data to anauthorizing entity. Once authorization is received by the server,clearance is sent to the point of sale device for completion of thetransaction. In this way, the conventional transaction processing methodinvolves an indirect path which causes undue overhead due to the use ofthe third-party server.

A need exists for a transaction authorization system which allows fobtransactions to be authorized while eliminating the cost associated withusing third-party servers.

In addition, conventional fobs are limited in that they must be used inproximity to the Point of Sale device. That is, for fob activation,conventional fobs must be positioned within the area of transmissioncast by the RF interrogation signal. More particularly, conventionalfobs are not affective for use in situations where the user wishes toconduct a transaction at a point of interaction such as a computerinterface.

Therefore, a need exists for a fob embodying RFID acquisitiontechnology, which is capable of use at a point of interaction device andwhich is additionally capable of facilitating transactions via acomputer interface connected to a network (e.g., the Internet).

Existing transponder-reader payment systems are also limited in that theconventional fob used in the systems is only responsive to oneinterrogation signal. Where multiple interrogation signals are used, thefob is only responsive to the interrogation signal to which it isconfigured. Thus, if the RFID reader of the system provides only aninterrogation signal to which the fob is incompatible, the fob will notbe properly activated.

Therefore, a need exists for a fob which is responsive to more than oneinterrogation signal.

Existing transponder-reader payment systems are additionally limited inthat the payment systems are typically linked to a funding sourceassociated with the transponder which includes a predetermined spendinglimit. Thus no flexibility is provided in instances where the payment isrequested which exceeds the predetermined spending limit. This istypically true since traditional methods for processing a requestedtransaction involve comparing the transaction to the spending limit orto an amount stored in a preloaded value data file prior to providingtransaction authorization to a merchant.

Thus, a system is needed which processes transponder-reader paymentrequests irrespective of the spending limit assigned to an associatedtransponder-reader payment system funding source.

Further, traditional transponder-reader systems do not permit the userto manage the system user account data. This is extremely problematicwhere the user wishes to change a transponder-reader system fundingsource to a source which provides more available spending room, or wherechanges are made to user's status (e.g., change in address, phonenumber, email, etc.) for which the transponder-reader account providerwishes to readily update the user's account.

Thus a need exists for a transponder-reader system which will allow theuser limited access to the transponder-reader account for managingaccount data.

Further still, existing transponder-reader systems do not permit meansfor automatically incenting the use of the fob associated with thesystem as opposed to the credit or charge card associated with the fob.That is, conventional transponder-reader systems do not provide a meansfor encouraging usage of the transponder reader system by encouraginguse of the fob product since the present systems do not distinguishbetween usage of a system transponder and a charge or credit cardaccount associated with the transponder.

Consequently, a need exists for a transponder-reader system which iscapable of determining when a system transponder is used, and incentingsuch usage.

Still further, present systems are limited in that the systems areunable to track credit or charge card usage and fob usage for a singlefunding source. For example, in typical prior art systems, a fob may belinked to a specified funding source (e.g., American Express,MasterCard, Visa, etc.) which may be used to provide funds forsatisfaction of a transaction request. The funding source mayadditionally have a consumer credit or charge card which may beassociated with the fob and which may be used for contact transactions.Where the credit or charge card is used, a statement reporting the cardusage is provided to the card user. However, the reporting statementdoes not include a reporting of the fob product usage. Thus, a fob useris unable to chart, analyze or compare fob usage to the usage of theassociated card. This is especially problematic where the funding sourceis used by more than one entity (e.g., spouses, multiple companypersonnel, etc.) where one entity may use the fob and a separate entitymay use the card associated with the fob.

Thus, a need exists for a transponder-reader payment system which wouldpermit reporting of the fob usage and the credit card usage in a singlefile.

SUMMARY OF THE INVENTION

Described herein is a system and method for using RFID technology toinitiate and complete financial transactions. The transponder-readerpayment system described herein may include an RFID reader operable toprovide a RF interrogation signal for powering a transponder system,receiving a transponder system RF signal, and providing transpondersystem account data relative to the transponder system RF signal. Thetransponder-reader payment system may include an RFID protocol/sequencecontroller in electrical communication with one or more interrogatorsfor providing an interrogation signal to a transponder, an RFIDauthentication circuit for authenticating the signal received from thetransponder, a serial or parallel interface for interfacing with a pointof interaction device, and an USB or serial interface for use inpersonalizing the RFID reader and/or the transponder. Thetransponder-reader payment system may further include a fob includingone or more transponders (e.g., modules) responsive to one or moreinterrogation signals and for providing an authentication signal forverifying that the transponder and/or the RFID reader are authorized tooperate within the transponder reader payment system. In this way, thefob may be responsive to multiple interrogation signals provided atdifferent frequencies. Further, the fob may include a USB or serialinterface for use with a computer network or with the RFID reader.

In one embodiment, the RFID reader receives, from the RFID transponderdevice, a code that is associated with a first funding source and asecond funding source. The RFID reader communicates a request associatedwith a transaction to a payment processor. The request includes the codeand the transaction is funded using the first funding source and thesecond funding source associated with the code. In one embodiment, thetransaction is funded according to a funding account protocol associatedwith the code.

The RFID system and method according to the present invention mayinclude an RFID transponder device which may be embodied in a fob, tag,card or any other form factor (e.g., wristwatch, keychain, cell phone,etc.), which may be capable of being presented for interrogation. Inthat regard, although the transponder is described herein as embodied ina fob, the invention is not so limited. The system may further includean RFID reader configured to send a standing RFID recognition signalwhich may be transmitted from the RFID reader via radio frequency (orelectromagnetic) propagation. The fob may be placed within proximity tothe RFID reader such that the RFID signal may interrogate the fob andinitialize fob identification procedures.

In one exemplary embodiment, as a part of the identification process,the fob and the RFID reader may engage in mutual authentication. TheRFID reader may identify the fob as including an authorized systemtransponder for receiving encrypted information and storing theinformation on the fob memory. Similarly, the fob, upon interrogation bythe RFID reader, may identify the RFID reader as authorized to 25receive the encrypted and stored information. Where the RFID reader andthe fob successfully mutually authenticate, the fob may transmit to theRFID reader certain information identifying the transaction account oraccounts to which the fob is associated. The RFID reader may receive theinformation and forward the information to facilitate the completion ofa transaction. In one exemplary embodiment, the RFID reader may forwardthe information to a point of interaction device (e.g., POS or computerinterface) for transaction completion. The mutual authorization processdisclosed herein aids in ensuring fob transponder-reader payment systemsecurity.

In another exemplary embodiment, the fob according to the presentinvention, includes means for completing transactions via a computerinterface. The fob may be connected to the computer using a USB orserial interface fob account information may be transferred to thecomputer for use in completing a transaction via a network (e.g., theInternet). In yet another exemplary embodiment of the present invention,a system is provided which incents usage of the transponder-readersystem transponder (e.g., fob). The system distinguishes between theusage of a fob and the usage of a charge or credit card sharing the samefunding source as the fob. Where the fob is used, the system may providereward points to the user based on criteria predetermined by the issuer.Additionally, where a preloaded fob system is used, the presentinvention recognizes when the associated fob preloaded value data fileis loaded or reloaded with funds. The invention then may provide rewardpoints based on the criteria associated with the loading or reloadingaction. Further, the system according to this invention may incentpatronage of a merchant. In this case, the system may receive a fobtransaction request and incent the fob user based on a marker or otheridentifier correlated with the merchant. The marker may be included inthe transaction identification, in a merchant identification providedwith the transaction, or a combination of both.

In still another exemplary embodiment of the invention, a system isdisclosed which enables the user to manage the account associated withthe fob. The user is provided limited access to all or a portion of thefob account information stored on the account provider database forupdating, for example, demographic information, account funding source,funding account protocol and/or account restrictions (e.g., spendinglimits, personal identification number, etc.). Access to all or aportion of the account may be provided to the user telephonically or viaa network (e.g., online).

In yet another exemplary embodiment of the invention, a system isprovided whereby the user is permitted to select one or more fundingsources for use in satisfying a merchant request. The user may switchfunding sources manually by, for example, contacting the fob accountprovider and indicating that a particular funding source is desired. Theuser may contact the provider or any other third party that canfacilitate changing the funding source via any means known in the artsuch as, for example, telephone, voice response, internet, cell phone,modem, email, webpage submission and/or any other electronic, optical ordigital methods for communication. In this way, the user is permitted tochange funding sources from a primary funding source to a secondaryfunding source. In this context, a “primary” funding source may be thefunding source which the account provider may primarily use to retrievefunds and satisfy all or a portion of a merchant transaction request. A“secondary” funding source may be any alternate funding source fromwhich value may be retrieved for satisfying all or a portion of atransaction request. It should be noted that primary and secondary areused herein to illustrate that more than one funding source may bechosen by the user for association with the fob, and that any number ofsources may be selected.

In addition, the fob user may provide the fob account provider with afunding protocol for use in determining which funding source to use. Forexample, the fob user may designate that for a particular merchant, typeof merchant or type of transaction, a selected funding source is to beautomatically used. In this way, the fob user is assured that particulartransactions will be satisfied (e.g., completed) using an identifiedfunding source and/or the fob account provider may send all similartransactions to an identified funding source, thereby facilitatingtracking of the similar transactions.

The funding protocol may additionally include guidelines forautomatically changing to a secondary funding source when the requestedtransaction amount meets or exceeds the available value of the primaryfunding source. That is, the funding protocol indicates to the accountprovider that the funds for satisfying the merchant request should beretrieved from a secondary funding source when the value in the primaryfunding source is insufficient for completing the transaction.Alternatively, the funding protocol may indicate to the account providerthat the transaction should be completed using value from both theprimary and secondary funding sources. The amount retrieved from theprimary and secondary funding sources may be based on a calculatedformula defined by the fob user or fob issuer. In a typical example,where a particular transaction or merchant is identified by the accountprovider (e.g., by use of the markers described above), the accountprovider may seek to retrieve a percentage of the value needed from theprimary funding source with the balance of the transaction retrievedfrom the secondary funding source. Alternatively, the value in theprimary funding source may be depleted prior to retrieving the balanceof the requested transaction from the secondary funding source.

In a further exemplary embodiment, the present invention providesmethods for processing a transaction request whereby the amount of thetransaction request may be approved prior to requesting funding from thefunding source and/or verifying that the amount for completing thetransaction is available. In this way, the transaction may be approvedprovided the transaction and/or account meets certain predeterminedauthorization criteria. Once the criteria is met, the transaction isauthorized and authorization is provided to the requesting agent (e.g.,merchant). In one instance the payment for the transaction is requestedfrom the funding source simultaneously to, or immediately following, theproviding of the authorization to the merchant.

In another instance the payment for transactions is requested at a timeperiod later than when the authorization is provided to the merchant.These features and other advantages of the system and method, as well asthe structure and operation of various exemplary embodiments of thesystem and method, are described below.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, wherein like numerals depict like elements,illustrate exemplary embodiments of the present invention, and togetherwith the description, serve to explain the principles of the invention.In the drawings:

FIG. 1A illustrates an exemplary RFID-based system in accordance withthe present invention, wherein exemplary components used for fobtransaction completion are depicted;

FIG. 1B illustrates an exemplary personalization system in accordancewith the present invention;

FIG. 2 is a schematic illustration of an exemplary fob in accordancewith the present invention;

FIG. 3 is a schematic illustration of an exemplary RFID reader inaccordance with the present invention;

FIG. 4 is an exemplary flow diagram of an exemplary authenticationprocess in accordance with the present invention;

FIG. 5 is an exemplary flow diagram of an exemplary decision process fora protocol/sequence controller in accordance with the present invention;

FIGS. 6A-B are an exemplary flow diagram of a fob personalizationprocess in accordance with the present invention;

FIGS. 7A-B are an exemplary flow diagram of an RFID readerpersonalization process in accordance with the present invention;

FIG. 8 is a flow diagram of an exemplary payment/transaction process inaccordance with the present invention;

FIG. 9 is another schematic illustration of an exemplary fob inaccordance with the present invention;

FIG. 10 is a depiction of an exemplary preloaded fob payment/transactionprocess in accordance with the present invention;

FIG. 11A is a depiction of an exemplary preloaded fob account preloadand reload processes in accordance with the present invention;

FIG. 11B is a depiction of an exemplary preloaded fob account reloadprocess in accordance with the present invention;

FIG. 12 is a depiction of an exemplary Direct Link payment/transactionprocess in accordance with the present invention;

FIG. 13 is a depiction of another exemplary payment/transaction processin accordance with the present invention; and

FIG. 14 is an exemplary flow diagram of a funding protocol for use bythe fob account provider in satisfying a transaction request.

DETAILED DESCRIPTION

The present invention may be described herein in terms of functionalblock components, screen shots, optional selections and variousprocessing steps. Such functional blocks may be realized by any numberof hardware and/or software components configured to perform tospecified functions. For example, the present invention may employvarious integrated circuit components, e.g., memory elements, processingelements, logic elements, look-up tables, and the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. Similarly, the softwareelements of the present invention may be implemented with anyprogramming or scripting language such as C, C++, Java, COBOL,assembler, PERL, extensible markup language (XML), JavaCard and MULTOSwith the various algorithms being implemented with any combination ofdata structures, objects, processes, routines or other programmingelements. Further, it should be noted that the present invention mayemploy any number of conventional techniques for data transmission,signaling, data processing, network control, and the like. For a basicintroduction on cryptography, review a text written by Bruce Schneierentitled “Applied Cryptography: Protocols, Algorithms, and Source Codein C,” published by John Wiley & Sons (second edition, 1996), hereinincorporated by reference.

In addition, many applications of the present invention could beformulated. The exemplary network disclosed herein may include anysystem for exchanging data or transacting business, such as theinternet, an intranet, an extranet, WAN, LAN, satellite communications,and/or the like. It is noted that the network may be implemented asother types of networks, such as an interactive television network(ITN).

Where required, the system user may interact with the system via anyinput device such as, a keypad, keyboard, mouse, kiosk, personal digitalassistant, handheld computer (e.g., Palm Pilot®, Blackberry® cellularphone and/or the like. Similarly, the invention could be used inconjunction with any type of personal computer, network computer, workstation, minicomputer, mainframe, or the like running any operatingsystem such as any version of Windows, Windows NT, Windows 2000, Windows98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, Solaris or the like.Moreover, although the invention may frequently be described as beingimplemented with TCP/IP communications protocol, it should be understoodthat the invention could also be implemented using SNA, IPX, Appletalk,IPte, NetBIOS, OSI or any number of communications protocols. Moreover,the system contemplates, the use, sale, or distribution of any goods,services or information over any network having similar functionalitydescribed herein.

FIG. 1A illustrates an exemplary RFID transaction system 100A inaccordance with the present invention, wherein exemplary components foruse in completing a fob transaction are depicted. In general, theoperation of system 100A may begin when fob 102 is presented forpayment, and is interrogated by RFID reader 104 or, alternatively,interface 134. Fob 102 and RFID reader 104 may then engage in mutualauthentication after which the transponder 102 may provide thetransponder identification and/or account identifier to the RFID reader104 which may further provide the information to the merchant system 130POS device 110.

System 100A may include a fob 102 having a transponder 114 and an RFIDreader 104 in RF communication with fob 102. Although the presentinvention is described with respect to a fob 102, the invention is notto be so limited. Indeed, system 100 may include any device having atransponder which is configured to communicate with an RFID reader 104via RF communication. Typical devices may include, for example, a keyring, tag, card, cell phone, wristwatch or any such form capable ofbeing presented for interrogation.

The RFID reader 104 may be configured to communicate using an RFIDinternal antenna 106. Alternatively, RFID reader 104 may include anexternal antenna 108 for communications with fob 102, where the externalantenna may be made remote to the RFID reader 104 using a suitable cableand/or data link 120. RFID reader 104 may be further in communicationwith a merchant system 130 via a data link 122. The system 100A mayinclude a transaction completion system including a point of interactiondevice such as, for example, a merchant point of sale (POS) device 110or a computer interface (e.g., user interface) 134. In one exemplaryembodiment the transaction completion system may include a merchantsystem 130 including the POS device 110 in communication with an RFIDreader 104 (via data link 122). As described more fully below, thetransaction completion system may include the user interface 134connected to a network 136 and to the transponder via a USB connector132.

Although the point of interaction device is described herein withrespect to a merchant point of sale (POS) device, the invention is notto be so limited. Indeed, a merchant POS device is used herein by way ofexample, and the point of interaction device may be any device capableof receiving fob account data. In this regard, the POS may be any pointof interaction device enabling the user to complete a transaction usinga fob 102. POS device 110 may be in further communication with acustomer interface 118 (via data link 128) for entering at least acustomer identity verification information. In addition, POS device 110may be in communication with a merchant host network 112 (via data link124) for processing any transaction request. In this arrangement,information provided by RFID reader 104 is provided to the POS device110 of merchant system 130 via data link 122. The POS device 110 mayreceive the information (and alternatively may receive any identityverifying information from customer interface 118 via data link 128) andprovide the information to host system 112 for processing.

A variety of conventional communications media and protocols may be usedfor data links 120, 122, 124, and 128. For example, data links 120, 122,124, and 128 may be an Internet Service Provider (ISP) configured tofacilitate communications over a local loop as is typically used inconnection with standard modem communication, cable modem, dishnetworks, ISDN, Digital Subscriber Lines (DSL), or any wirelesscommunication media. In addition, the merchant system 130 including thePOS device 110 and host network 112 may reside on a local area networkwhich interfaces to a remote network (not shown) for remoteauthorization of an intended transaction. The merchant system 130 maycommunicate with the remote network via a leased line, such as a T1, D3line, or the like. Such communications lines are described in a varietyof texts, such as, “Understanding Data Communications,” by Gilbert Held,which is incorporated herein by reference.

An account number, as used herein, may include any identifier for anaccount (e.g., credit, charge debit, checking, savings, reward, loyalty,or the like) which may be maintained by a transaction account provider(e.g., payment authorization center) and which may be used to complete afinancial transaction. A typical account number (e.g., account data) maybe correlated to a credit or debit account, loyalty account, or rewardsaccount maintained and serviced by such entities as American Express®,Visa® and/or MasterCard® or the like. For ease in understanding, thepresent invention may be described with respect to a credit account.However, it should be noted that the invention is not so limited andother accounts permitting an exchange of goods and services for anaccount data value is contemplated to be within the scope of the presentinvention.

In addition, the account number (e.g., account data) may be associatedwith any device, code, or other identifier/indicia suitably configuredto allow the consumer to interact or communicate with the system, suchas, for example, authorization/access code, personal identificationnumber (PIN), Internet code, digital certificate, biometric data, and/orother identification indicia. The account number may be optionallylocated on a rewards card, charge card, credit card, debit card, prepaidcard, telephone card, smart card, magnetic stripe card, bar code card,and/or the like. The account number may be distributed and stored in anyform of plastic, electronic, magnetic, and/or optical device capable oftransmitting or downloading data to a second device. A customer accountnumber may be, for example, a sixteen-digit credit card number, althougheach credit provider has its own numbering system, such as thefifteen-digit numbering system used by American Express®. Each company'scredit card numbers comply with that company's standardized format suchthat the company using a sixteen-digit format will generally use fourspaced sets of numbers, as represented by the number “0000 0000 00000000”. In a typical example, the first five to seven digits are reservedfor processing purposes and identify the issuing bank, card type and,etc. In this example, the last sixteenth digit is used as a sum checkfor the sixteen-digit number. The intermediary eight-to-ten digits areused to uniquely identify the customer. The account number stored asTrack 1 and Track 2 data as defined in ISO/IEC 7813, and further may bemade unique to fob 102. In one exemplary embodiment, the account numbermay include a unique fob serial number and user identification number,as well as specific application applets. The account number may bestored in fob 102 inside a database 214, as described more fully below.Database 214 may be configured to store multiple account numbers issuedto the fob 102 user by the same or different account providinginstitutions. Where the account data corresponds to a loyalty or rewardsaccount, the database 214 may be configured to store the attendantloyalty or rewards points data.

FIG. 2 illustrates a block diagram of the many functional blocks of anexemplary fob 102 in accordance with the present invention. Fob 102 maybe an RFID fob 102 which may be presented by the user to facilitate anexchange of funds or points, etc., for receipt of goods or services. Asdescribed herein, by way of example, the fob 102 may be an RFID fobwhich may be presented for facilitating payment for goods and/orservices.

Fob 102 may include an antenna 202 for receiving an interrogation signalfrom RFID reader 104 via antenna 106 (or alternatively, via externalantenna 108). Fob antenna 202 may be in communication with a transponder114. In one exemplary embodiment, transponder 114 may be a 13.56 MHztransponder compliant with the ISO/IEC 14443 standard, and antenna 202may be of the 13 MHz variety. The transponder 114 may be incommunication with a transponder compatible modulator/demodulator 206configured to receive the signal from transponder 114 and configured tomodulate the signal into a format readable by any later connectedcircuitry. Further, modulator/demodulator 206 may be configured toformat (e.g., demodulate) a signal received from the later connectedcircuitry in a format compatible with transponder 114 for transmittingto RFID reader 104 via antenna 202. For example, where transponder 114is of the 13.56 MHz variety, modulator/demodulator 206 may be ISO/IEC14443-2 compliant.

Modulator/demodulator 206 may be coupled to a protocol/sequencecontroller 208 for facilitating control of the authentication of thesignal provided by RFID reader 104, and for facilitating control of thesending of the fob 102 account number. In this regard, protocol/sequencecontroller 208 may be any suitable digital or logic driven circuitrycapable of facilitating determination of the sequence of operation forthe fob 102 inner-circuitry. For example, protocol/sequence controller208 may be configured to determine whether the signal provided by theRFID reader 104 is authenticated, and thereby providing to the RFIDreader 104 the account number stored on fob 102.

Protocol/sequence controller 208 may be further in communication withauthentication circuitry 210 for facilitating authentication of thesignal provided by RFID reader 104. Authentication circuitry may befurther in communication with a non-volatile secure memory database 212.Secure memory database 212 may be any suitable elementary file systemsuch as that defined by ISO/IEC 7816-4 or any other elementary filesystem allowing a lookup of data to be interpreted by the application onthe chip. Database 212 may be any type of database, such as relational,hierarchical, object-oriented, and/or the like. Common database productsthat may be used to implement the databases include DB2 by IBM (WhitePlains, N.Y.), any of the database products available from OracleCorporation (Redwood Shores, Calif.), Microsoft Access or MSSQL byMicrosoft Corporation (Redmond, Wash.), or any other database product.Database 212 may be organized in any suitable manner, including as datatables or lookup tables. Association of certain data may be accomplishedthrough any data association technique known and practiced in the art.For example, the association may be accomplished either manually orautomatically. Automatic association techniques may include, forexample, a database search, a database merge, GREP, AGREP, SQL, and/orthe like. The association step may be accomplished by a database mergefunction, for example, using a “key field” in each of the manufacturerand retailer data tables. A “key field” partitions the databaseaccording to the high-level class of objects defined by the key field.For example, a certain class may be designated as a key field in boththe first data table and the second data table, and the two data tablesmay then be merged on the basis of the class data in the key field. Inthis embodiment, the data corresponding to the key field in each of themerged data tables is preferably the same. However, data tables havingsimilar, though not identical, data in the key fields may also be mergedby using AGREP, for example.

The data may be used by protocol/sequence controller 208 for dataanalysis and used for management and control purposes, as well assecurity purposes. Authentication circuitry may authenticate the signalprovided by RFID reader 104 by association of the RFID signal toauthentication keys stored on database 212. Encryption circuitry may usekeys stored on database 212 to perform encryption and/or decryption ofsignals sent to or from the RFID reader 104.

In addition, protocol/sequence controller 208 may be in communicationwith a database 214 for storing at least a fob 102 account data, and aunique fob 102 identification code. Protocol/sequence controller 208 maybe configured to retrieve the account number from database 214 asdesired. Database 214 may be of the same configuration as database 212described above. The fob account data and/or unique fob identificationcode stored on database 214 may be encrypted prior to storage. Thus,where protocol/sequence controller 208 retrieves the account data, andor unique fob identification code from database 214, the account numbermay be encrypted when being provided to RFID reader 104. Further, thedata stored on database 214 may include, for example, an unencryptedunique fob 102 identification code, a user identification, Track 1 and 2data, as well as specific application applets. Fob 102 may be configuredto respond to multiple interrogation frequency transmissions provided byRFID reader 104. That is, as described more fully below, RFID reader 104may provide more than one RF interrogation signal. In this case, fob 102may be configured to respond to the multiple frequencies by including infob 102 one or more additional RF signal receiving/transmitting units226. RF signal receiving/transmitting unit 226 may include an antenna218 and transponder 220 where the antenna 218 and transponder 220 arecompatible with at least one of the additional RF signals provided byRFID reader 104. For example, in one exemplary embodiment, fob 102 mayinclude a 134 KHz antenna 218 configured to communicate with a 134 KHztransponder 220. In this exemplary configuration, an ISO/IEC 14443-2compliant modulator/demodulator may not be required. Instead, the 134KHz transponder may be configured to communicate directly with theprotocol/sequence controller 208 for transmission and receipt ofauthentication and account number signals as described above.

In another embodiment, fob 102 may further include a universal serialbus (USB) connector 132 for interfacing fob 102 to a user interface 134.User interface 134 may be further in communication with a POS device 110via a network 136. Network 136 may be the Internet, an intranet, or thelike as is described above with respect to network 112. Further, theuser interface 134 may be similar in construction to any conventionalinput devices and/or computing systems aforementioned for permitting thesystem user to interact with the system. In one exemplary embodiment,fob 102 may be configured to facilitate online Internet payments. A USBconverter 222 may be in communication with a USB connector 232 forfacilitating the transfer of information between themodulator/demodulator 206 and USB connector 132. Alternatively, USBconverter 222 may be in communication with protocol/sequence controller208 to facilitate the transfer of information between protocol/sequencecontroller 208 and USB connector 132.

Where fob 102 includes a USB connector 132, fob 102 may be incommunication with, for example, a USB port on user interface 134. Theinformation retrieved from fob 102 may be compatible with credit cardand/or smart card technology enabling usage of interactive applicationson the Internet. No RFID reader may be required in this embodiment sincethe connection to POS device 110 may be made using a USB port on userinterface 134 and a network 136.

Fob 102 may include means for enabling activation of the fob by theuser. In one exemplary embodiment, a switch 230 which may be operated bythe user of the fob 102. The switch 230 on fob 102 may be used toselectively or inclusively activate the fob 102 for particular uses. Inthis context, the term “selectively” may mean that the switch 230enables the user to place the fob 102 in a particular operational mode.For example, the user may place the fob 102 in a mode for enablingpurchase of a good or of a service using a selected account number.Alternatively, the fob may be placed in a mode as such that the fobaccount number is provided by USB port 132 (or serial port) only and thefob transponder 114 is disabled. In addition, the term “inclusively” maymean that the fob 102 is placed in an operational mode permitting thefob 102 to be responsive to the RF interrogation and interrogation viathe USB connector 132. In one particular embodiment, the switch 230 mayremain in an OFF position ensuring that one or more applications oraccounts associated with the fob 102 are non-reactive to any commandsissued by RFID reader 104. As used herein, the OFF position may betermed the “normal” position of the activation switch 230, althoughother normal positions are contemplated.

In another exemplary embodiment, when the switch 230 is moved from theOFF position, the fob 102 may be deemed activated by the user. That is,the switch 230 may activate internal circuitry in fob 102 for permittingthe fob to be responsive to RF signals (e.g., commands from RFID reader104). In this way, switch 230 may facilitate control of the active andinactive states of the fob 102. Such control increases the systemsecurity by preventing inadvertent or illegal use of the fob 102.

In one exemplary embodiment, switch 230 may be a simple mechanicaldevice in communication with circuitry which may electrically preventthe fob from being powered by an RFID reader. That is, when switch 230is in its normal position, switch 230 may provide a short to the fob 102internal circuitry, preventing fob 102 from being responsive tointerrogation by RF or via the USB connector 230. In this arrangement,the switch 230 may be, for example, a “normally closed” (NC) configuredswitch, which may be electrically connected to the antenna 202 at theinterface of the antenna 202 and the transponder 114. The switch 230 maybe depressed, which may open the switch 230 fully activating the antenna202.

In yet another exemplary embodiment, the fob 102 may include a biometricsensor and biometric membrane configured to operate as switch 230 andactivate the fob 102 when provided biometric signal from the fob 102user. Such biometric signal may be the digital reading of a fingerprint,thumbprint, or the like. Typically, where biometric circuitry is used,the biometric circuitry may be powered by an internal voltage source(e.g., battery). In this case, the switch may not be a simple mechanicaldevice, but a switch which is powered. In yet another exemplaryembodiment, switch 230 may be battery powered though no biometriccircuitry is present in the fob 102.

In yet another embodiment, the switch 230 may be a logic switch. Whereswitch 230 is a logic switch the switch 230 control software may be readfrom the sequence controller 208 to selectively control the activationof the various fob 102 components.

FIG. 3 illustrates an exemplary block diagram of an RFID reader 104 inaccordance with an exemplary embodiment of the present invention. RFIDreader 104 includes, for example, an antenna 106 coupled to a RF module302, which is further coupled to a control module 304. In addition, RFIDreader 104 may include an antenna 108 positioned remotely from the RFIDreader 104 and coupled to RFID reader 104 via a suitable cable 120, orother wire or wireless connection.

RF module 302 and antenna 106 may be suitably configured to facilitatecommunication with fob 102. Where fob 102 is formatted to receive asignal at a particular RF frequency, RF module 302 may be configured toprovide an interrogation signal at that same frequency. For example, inone exemplary embodiment, fob 102 may be configured to respond to aninterrogation signal of about 13.56 MHz. In this case, RFID antenna 106may be 13 MHz and may be configured to transmit an interrogation signalof about 13.56 MHz. That is, fob 102 may be configured to include afirst and second RF module (e.g., transponder) where the first modulemay operate using a 134 kHz frequency and the second RF module mayoperate using a 13.56 MHz frequency. The RFID reader 104 may include tworeceivers which may operate using the 134 kHz frequency, the 13.56 MHzfrequency or both. When the reader 104 is operating at 134 kHzfrequency, only operation with the 134 kHz module on the fob 102 may bepossible. When the reader 104 is operating at the 13.56 MHz frequency,only operation with the 13.56 MHz module on the fob 102 may be possible.Where the reader 104 supports both a 134 kHz frequency and a 13.56 MHzRF module, the fob 102 may receive both signals from the reader 104. Inthis case, the fob 102 may be configured to prioritize selection of theone or the other frequency and reject the remaining frequency.Alternatively, the reader 104 may receive signals at both frequenciesfrom the fob upon interrogation. In this case, the reader 104 may beconfigured to prioritize selection of one or the other frequency andreject the remaining frequency.

Further, protocol/sequence controller 314 may include an optionalfeedback function for notifying the user of the status of a particulartransaction. For example, the optional feedback may be in the form of anLED, LED screen and/or other visual display which is configured to lightup or display a static, scrolling, flashing and/or other message and/orsignal to inform the fob 102 user that the transaction is initiated(e.g., fob is being interrogated), the fob is valid (e.g., fob isauthenticated), transaction is being processed, (e.g., fob accountnumber is being read by RFID reader) and/or the transaction is acceptedor denied (e.g., transaction approved or disapproved). Such an optionalfeedback may or may not be accompanied by an audible indicator (or maypresent the audible indicator singly) for informing the fob 102 user ofthe transaction status. The audible feedback may be a simple tone,multiple tones, musical indicator, and/or voice indicator configured tosignify when the fob 102 is being interrogated, the transaction status,or the like.

RFID antenna 106 may be in communication with a transponder 306 fortransmitting an interrogation signal and receiving at least one of anauthentication request signal and/or an account data from fob 102.Transponder 306 may be of similar description as transponder 114 of FIG.2. In particular, transponder 306 may be configured to send and/orreceive RF signals in a format compatible with antenna 202 in similarmanner as was described with respect to fob transponder 114. Forexample, where transponder 306 is 13.56 MHz RF rated antenna 202 may be13.56 MHz compatible. Similarly, where transponder 306 is ISO/IEC 14443rated, antenna 106 may be ISO/IEC 14443 compatible.

RF module 302 may include, for example, transponder 306 in communicationwith authentication circuitry 308 which may be in communication with asecure database 310. Authentication circuitry 308 and database 310 maybe of similar description and operation as described with respect toauthentication circuitry 210 and secure memory database 212 of FIG. 2.For example, database 310 may store data corresponding to the fob 102which are authorized to transact business over system 100. Database 310may additionally store RFID reader 104 identifying information forproviding to fob 102 for use in authenticating whether RFID reader 104is authorized to be provided the fob account number stored on fobdatabase 214.

Authentication circuitry 308 may be of similar description and operationas authentication circuitry 210. That is, authentication circuitry 308may be configured to authenticate the signal provided by fob 102 insimilar manner that authentication circuitry 210 may be configured toauthenticate the signal provided by RFID reader 104. As is describedmore fully below, fob 102 and RFID reader 104 engage in mutualauthentication. In this context, “mutual authentication” may mean thatoperation of the system 100 may not take place until fob 102authenticates the signal from RFID reader 104, and RFID reader 104authenticates the signal from fob 102.

FIG. 4 is a flowchart of an exemplary authentication process inaccordance with the present invention. The authentication process isdepicted as one-sided. That is, the flowchart depicts the process of theRFID reader 104 authenticating the fob 102, although similar steps maybe followed in the instance that fob 102 authenticates RFID reader 104.

As noted, database 212 may store security keys for encrypting ordecrypting signals received from RFID reader 104. In an exemplaryauthentication process, where RFID reader 104 is authenticating fob 102,RFID reader 104 may provide an interrogation signal to fob 102 (step402). The interrogation signal may include a random code generated bythe RFID reader authentication circuit 210, which is provided to the fob102 and which is encrypted using an unique encryption key correspondingto the fob 102 unique identification code. For example, theprotocol/sequence controller 314 may provide a command to activate theauthentication circuitry 308. Authentication circuitry 308 may providefrom database 310 a fob interrogation signal including a random numberas a part of the authentication code generated for each authenticationsignal. The authentication code may be an alphanumeric code which isrecognizable (e.g., readable) by the RFID reader 104 and the fob 102.The authentication code may be provided to the fob 102 via the RFID RFinterface 306 and antenna 106 (or alternatively antenna 108).

Fob 102 receives the interrogation signal (step 404). The interrogationsignal including the authorization code may be received at the RFinterface 114 via antenna 202. Once the fob 102 is activated, theinterrogation signal including the authorization code may be provided tothe modulator/demodulator circuit 206 where the signal may bedemodulated prior to providing the signal to protocol/sequencecontroller 208. Protocol/sequence controller 208 may recognize theinterrogation signal as a request for authentication of the fob 102, andprovide the authentication code to authentication circuit 210. The fob102 may then encrypt the authentication code (step 406). In particular,encryption may be done by authentication circuit 210, which may receivethe authentication code and encrypt the code prior to providing theencrypted authentication code to protocol/sequence controller 208. Fob102 may then provide the encrypted authentication code to the RFIDreader 104 (step 408). That is, the encrypted authentication code may beprovided to the RFID reader 104 via modulator/demodulator circuit 206,RF interface 114 (e.g., transponder 114) and antenna 202.

RFID reader 104 may then receive the encrypted authentication code anddecryption it (step 410). That is, the encrypted authentication code maybe received at antenna 106 and RF interface 306 and may be provided toauthentication circuit 308. Authentication circuit 308 may be provided asecurity authentication key (e.g., transponder system decryption key)from database 310. The authentication circuit may use the authenticationkey to decrypt (e.g., unlock) the encrypted authorization code. Theauthentication key may be provided to the authentication circuit basedon the fob 102 unique identification code. For example, the encryptedauthentication code may be provided along with the unique fob 102identification code. The authentication circuit may receive the fob 102unique identification code and retrieve from the database 310 atransponder system decryption key correlative to the unique fob 102identification code for use in decrypting the encrypted authenticationcode.

Once the authentication code is decrypted, the decrypted authenticationcode is compared to the authentication code provided by the RFID reader104 at step 402 (step 412) to verify its authenticity. If the decryptedauthorization code is not readable (e.g., recognizable) by theauthentication circuit 308, the fob 102 is deemed to be unauthorized(e.g., unverified) (step 416) and the operation of system 100 isterminated (step 418). Contrarily, if the decrypted authorization codeis recognizable (e.g., verified) by the fob 102, the decryptedauthorization code is deemed to be authenticated (step 412), and thetransaction is allowed to proceed (step 414). In one particularembodiment, the proceeding transaction may mean that the fob 102 mayauthenticate the RFID reader 104 prior to the RFID reader 104authenticating fob 102, although, it should be apparent that the RFIDreader 104 may authenticate the fob 102 prior to the fob 102authenticating the RFID reader 104.

It should be noted that in an exemplary verification process, theauthorization circuit 308 may determine whether the unlockedauthorization code is identical to the authorization code provided instep 402. If the codes are not identical then the fob 102 is notauthorized to access system 100. Although, the verification process isdescribed with respect to identicality, identicality is not required.For example, authentication circuit 308 may verify the decrypted codethrough any protocol, steps, or process for determining whether thedecrypted code corresponds to an authorized fob 102.

Authentication circuitry 308 may additionally be in communication with aprotocol/sequence controller 314 of similar operation and description asprotocol/sequence controller 208 of FIG. 2. That is, protocol/sequencedevice controller 314 may be configured to determine the order ofoperation of the RFID reader 104 components. For example, FIG. 5illustrates and exemplary decision process under which protocol/sequencecontroller 314 may operate. Protocol/sequence controller 314 may commandthe different components of RFID reader 104 based on whether a fob 102is present (step 502). For example, if a fob 102 is not present, thenprotocol/sequence controller 314 may command the RFID reader 104 toprovide an uninterrupted interrogation signal (step 504). That is, theprotocol/sequence controller may command the authentication circuit 308to provide an uninterrupted interrogation signal until the presence of afob 102 is realized. If a fob 102 is present, the protocol/sequencecontroller 314 may command the RFID reader 104 to authenticate the fob102 (step 506).

As noted above, authentication may mean that the protocol/sequencecontroller 314 may command the authentication circuit 308 to provide fob102 with an authorization code. If a response is received from fob 102,protocol/sequence controller may determine if the response is a responseto the RFID reader 104 provided authentication code, or if the responseis a signal requiring authentication (step 508). If the signal requiresauthentication, then the protocol/sequence controller 314 may activatethe authentication circuit as described above (step 506). On the otherhand, if the fob 102 signal is a response to the provided authenticationcode, then the protocol/sequence controller 314 may command the RFIDreader 104 to retrieve the appropriate security key for enablingrecognition of the signal (step 510). That is, the protocol/sequencecontroller 314 may command the authentication circuit 308 to retrievefrom database 310 a security key (e.g., transponder system decryptionkey), unlock the signal, and compare the signal to the signal providedby the RFID reader 104 in the authentication process (e.g., step 506).If the signal is recognized, the protocol/sequence controller 314 maydetermine that the fob 102 is authorized to access the system 100. Ifthe signal is not recognized, then the fob 102 is considered notauthorized. In which case, the protocol/sequence controller 314 maycommand the RFID controller to interrogate for authorized fobs (step504).

Once the protocol/sequence controller determines that the fob 102 isauthorized, the protocol/sequence controller 314 may seek to determineif additional signals are being sent by fob 102 (step 514). If noadditional signal is provided by fob 102, then the protocol/sequencecontroller 314 may provide all the components of RFID reader 104 toremain idle until such time as a signal is provided (step 516).Contrarily, where an additional fob 102 signal is provided, theprotocol/sequence controller 314 may determine if the fob 102 isrequesting access to the merchant point of sale terminal 110 (e.g., POSdevice) or if the fob 102 is attempting to interrogate the RFID reader104 for return (e.g., mutual) authorization (step 518). Where the fob102 is requesting access to a merchant point of sale terminal 110, theprotocol/sequence controller 314 may command the RFID reader 104 to opencommunications with the point of sale terminal 110 (step 524). Inparticular, the protocol/sequence controller 314 may command the pointof sale terminal communications interface 312 to become active,permitting transfer of data between the RFID reader 104 and the merchantpoint of sale terminal 110.

On the other hand, if the protocol/sequence controller determines thatthe fob 102 signal is a mutual interrogation signal, then theprotocol/sequence controller may command the RFID reader 104 to encryptthe signal (step 520). The protocol/sequence controller 314 may commandthe encryption authentication circuit 318 to retrieve from database 320the appropriate encryption key in response to the fob 102 mutualinterrogation signal. The protocol/sequence controller 314 may thencommand the RFID reader 104 to provide the encrypted mutualinterrogation signal to the fob 102. The protocol/sequence controller314 may command the authentication circuit 318 to provide an encryptedmutual interrogation signal for the fob 102 to mutually authenticate.Fob 102 may then receive the encrypted mutual interrogation signal andretrieve from authentication circuitry 212 an RFID reader decryptionkey.

Although an exemplary decision process of protocol/sequence controller314 is described, it should be understood that a similar decisionprocess may be undertaken by protocol/sequence controller 208 incontrolling the components of fob 102. Indeed, as described above,protocol/sequence controller 314 may have similar operation and designas protocol/sequence controller 208. In addition, to the above,protocol/sequence controllers 208 and 314 may incorporate in thedecision process appropriate commands for enabling USB interfaces 222and 316, when the corresponding device is so connected.

Encryption/decryption component 318 may be further in communication witha secure account number database 320 which stores the security keysnecessary for decrypting the encrypted fob account number. Uponappropriate request from protocol/sequence controller 314,encryption/decryption component (e.g., circuitry 318) may retrieve theappropriate security key, decrypt the fob account number and forward thedecrypted account number to protocol sequence controller 314 in anyformat readable by any later connected POS device 110. In one exemplaryembodiment, the account number may be forwarded in a conventionalmagnetic stripe format compatible with the ISO/IEC 7813 standard. Uponreceiving the account number in magnetic stripe format,protocol/sequence controller 314 may forward the account number to POSdevice 110 via a communications interface 312 and data link 122, as bestshown in FIG. 1. POS device 110 may receive the decrypted account numberand forward the magnetic stripe formatted account number to a merchantnetwork 112 for processing under the merchant's business as usualstandard. In this way, the present invention eliminates the need of athird-party server. Further, where the POS device 110 receives aresponse from network 112 (e.g., transaction authorized or denied),protocol/sequence controller 314 may provide the network response to theRF module 302 for optically and/or audibly communicating the response tothe fob 102 user.

RFID reader 104 may additionally include a USB interface 316, incommunication with the protocol/sequence controller 314. In oneembodiment, the USB interface may be a RS22 serial data interface.Alternatively, the RFID reader 104 may include a serial interface suchas, for example, a RS232 interface in communication with theprotocol/sequence controller 314. The USB connector 316 may be incommunication with a personalization system 116 (shown in FIG. 1B) forinitializing RFID reader 104 to system 100 application parameters. Thatis, prior to operation of system 100, RFID reader 104 may be incommunication with personalization system 116 for populating database310 with a listing of security keys belonging to authorized fobs 102,and for populating database 320 with the security keys to decrypt thefob 102 account numbers placing the account numbers in ISO/IEC 7813format. In this way, RFID reader 104 may be populated with a uniqueidentifier (e.g., serial number) which may be used by fob authenticationcircuitry 210 to determine if RFID reader 104 is authorized to receive afob 102 encrypted account number.

FIG. 1B illustrates an exemplary personalization system 100B, inaccordance with the present invention. In general, typicalpersonalization system 100B may be any system for initializing the RFIDreader 104 and fob 102 for use in system 100A. With reference to FIG.1B, the similar personalization process for fob 102 may be illustrated.For example, personalization system 116 may be in communication with fob102 via RF ISO 14443 interface 114 for populating fob database 212 withthe security keys for facilitating authentication of the unique RFIDreader 104 identifier. In addition, personalization system 116 maypopulate on database 212 a unique fob 102 identifier for use by RFIDreader 104 in determining whether fob 102 is authorized to access system100. Personalization system 116 may populate (e.g., inject) theencrypted fob 102 account number into fob database 214 for laterproviding to an authenticated RFID reader 104.

In one exemplary embodiment, personalization system 116 may include anystandard computing system as described above. For example,personalization system 116 may include a standard personal computercontaining a hardware security module operable using any conventionalgraphic user interface. Prior to populating the security key informationaccount number and unique identifying information into the fob 102 orRFID reader 104, the hardware security module may authenticate the fob102 and RFID reader 104 to verify that the components are authorized toreceive the secure information.

FIGS. 6A-B illustrate an exemplary flowchart of a personalizationprocedure which may be used to personalize fob 102 and/or RFID reader104. Although the following description discusses mainly personalizationof fob 102, RFID reader 104 may be personalized using a similar process.The personalization process, which occurs between the personalizationsystem 116 and the device to be personalized (e.g., fob 102 or RFIDreader 104), may begin, for example at step 602. Mutual authenticationmay occur between the personalization system 116 and the device to beauthenticated in much the same manner as was described above with regardto fob 102 mutually authenticating with RFID reader 104. That is,personalization system 116 may transmit a personalization system 116identifier to the device to be authenticated which is compared by thedevice authentication circuitry 210, 308 against personalization systemidentifiers stored in the device database 212, 310. Where a match doesnot occur (step 604), the personalization process may be aborted (step612). Where a match occurs (step 604), the personalization system mayprepare a personalization file to be provided to the device to bepersonalized (step 606). If the personalization system is operatedmanually, the personalization file may be entered into thepersonalization system 116 using any suitable system interface such as,for example, a keyboard (step 606). Where the personalization system 116operator elects to delay the preparation of the personalization files,the system 116 may abort the personalization process (step 610). In thiscontext, the personalization file may include the unique fob 102 or RFIDreader 104 identifier, security key for loading into database 212 and310, and/or security keys for decrypting a fob account number which maybe loaded in database 320.

Fob 102 may be personalized by direct connection to the personalizationsystem 116 via RF ISO/IEC 14443 interface 114, or the fob 102 may bepersonalized using RFID reader 104. Personalization system 116 and RFIDreader 104 may engage in mutual authentication and RFID reader 104 maybe configured to transmit the fob personalization file to fob 102 viaRF. Once the fob 102 is presented to RFID reader 104 (steps 608, 614)for personalization, fob 102 and RFID reader 104 may engage in mutualauthentication (step 614). Where the fob 102 is not presented to theRFID reader 104 for personalization, the personalization process may beaborted (step 610).

If the fob 102 is detected, the personalization system 116 may create asa part of the personalization file, a unique identifier for providing tothe fob 102 (step 616). The identifier is unique in that one identifiermay be given only to a single fob. That is, no other fob may have thatsame identifier. The fob may then be configured and loaded with thatidentifier (step 618).

The encrypted fob 102 account number may be populated into fob 102 inthe same manner as is described with respect to the fob 102 uniqueidentifier. That is, personalization system 116 may pre-encrypt theaccount data (step 640) and inject the encrypted account into fobdatabase 214 (step 622). The encrypted account data may be loaded (e.g.,injected) into the fob 102 using RFID reader 104 as discussed above.

Once the personalization file is populated into the fob 102, thepopulated information is irreversibly locked to prevent alteration,unauthorized reading and/or unauthorized access (step 624).Personalization system 116 may then create a log of the personalizationfile information for later access and analysis by the personalizationsystem 116 user (step 626).

It should be noted that in the event the personalization process iscompromised or interrupted (step 628), the personalization system 116may send a security alert to the user (step 630) and the personalizationprocess may be aborted (step 612). On the other hand, where no suchcompromising or interruption exists, the personalization system 116 maybe prepared to begin initialization on a second device to bepersonalized (step 632).

FIGS. 7A-B illustrate another exemplary embodiment of a personalizationprocess which may be used to personalize RFID reader 104. RFID reader104 may be in communication with a personalization system 116 via anRFID reader USB connection 316 (step 702). Once connected,personalization system 116 may establish communications with the RFIDreader 104 and RFID reader 104 may provide personalization system 116any RFID reader 104 identification data presently stored on the RFIDreader 104 (step 704). In accordance with step 708, where the RFIDreader 104 is being personalized for the first time (step 706) the RFIDreader 104 and the personalization system 116 may engage in mutualauthentication as described above with respect to FIGS. 6A-B. After themutual authentication is complete, personalization system 116 may verifythat RFID reader 104 is properly manufactured or configured to operatewithin system 100. The verification may include evaluating the operationof the RFID reader 104 by determining if the RFID reader will acceptpredetermined default settings. That is, the personalization system 116may then provide the RFID reader 104 a set of default settings (step708) and determine if the RFID reader 104 accepts those settings (step712). If RFID reader 104 does not accept the default settings,personalization system 116 may abort the personalization process (step714).

If the personalization system 116 determines that the personalizationprocess is not the first personalization process undertaken by the RFIDreader 104 (step 706), personalization system 116 and RFID reader 104may engage in a mutual authentication process using the existingsecurity keys already stored on RFID reader 104 (step 710). Ifauthentication is unsuccessful (step 712), the personalization system116 may abort the personalization process (step 714).

Where the personalization system 116 and the RFID reader 104successfully mutually authenticate, the personalization system 116 mayupdate the RFID reader 104 security keys (step 716). Updating thesecurity keys may take place at any time as determined by a system 100manager. The updating may take place as part of a routine maintenance ormerely to install current security key data. The updating may beperformed by downloading firmware into RFID reader 104 (step 718). Inthe event that the personalization system 116 determines in step 706that the RFID reader 104 is undergoing an initial personalization, thefirmware may be loaded into the RFID reader 104 for the first time. Inthis context, “firmware” may include any file which enables the RFIDreader 102 to operate under system 100 guidelines. For example, suchguidelines may be directed toward the operation of RFID readerprotocol/sequence controller 314.

Personalization system 116 may then determine if the personalizationkeys (e.g., security keys, decryption keys, RFID identifier) need to beupdated or if the RFID reader 104 needs to have an initial installationof the personalization keys (step 720). If so, then personalizationsystem 116 may download the personalization keys as appropriate (step722).

Personalization system 116 may then check the RFID reader 104 todetermine if the fob 102 identifiers and corresponding security keysshould be updated or initially loaded (step 724). If no updating isnecessary the personalization system 116 may end the personalizationprocedure (step 732). Contrarily, if the personalization system 116determines that the fob 102 identifiers and corresponding keys need tobe updated or installed, the personalization system 116 may download theinformation onto RFID reader 104 (step 726). The information (e.g., fobsecurity keys and identifiers) may be downloaded in an encrypted formatand the RFID reader 104 may store the information in the RFID readerdatabase 310 as appropriate (step 728). The personalization system 116may then create or update a status log cataloging for later use andanalysis by the personalization system 116 user (step 730). Uponupdating the status log, the personalization process may be terminated(step 732).

It should be noted that, in some instances it may be necessary torepersonalize the RFID reader in similar manner as described above. Inthat instance, the personalization process described in FIGS. 7A and 7Bmay be repeated.

FIG. 8 illustrates an exemplary flow diagram for the operation of system100A. The operation may be understood with reference to FIG. 1A, whichdepicts the elements of system 100A which may be used in an exemplarytransaction. The process is initiated when a customer desires to presenta fob 102 for payment (step 802). Upon presentation of the fob 102, themerchant initiates the RF payment procedure via an RFID reader 104 (step804). In particular, the RFID reader sends out an interrogation signalto scan for the presence of fob 102 (step 806). The RF signal may beprovided via the RFID reader antenna 106 or optionally via an externalantenna 108. The customer then may present the fob 102 for payment (step808) and the fob 102 is activated by the RF interrogation signalprovided.

The fob 102 and the RFID reader 104 may then engage in mutualauthentication (step 810). Where the mutual authentication isunsuccessful, an error message may be provided to the customer via theRFID optical and/or audible indicator (step 814) and the transaction maybe aborted (step 816). Where the mutual authentication is successful(step 814), the RFID reader 104 may provide the customer with anappropriate optical and/or audible message (e.g., “transactionprocessing” or “wait”) (step 818). The fob protocol/sequence controller208 may then retrieve from database 214 an encrypted fob account numberand provide the encrypted account number to the RFID reader 104 (step820).

The RFID reader 104 may then decrypt the account number and convert theaccount number into magnetic stripe (ISO/IEC 7813) format (step 822) andprovide the unencrypted account number to the merchant system 130 (step828). In particular, the account number may be provided to the POS 110device for transmission to the merchant network 112 for processing.Exemplary processing methods according to the present invention arediscussed with respect to FIGS. 10-13, shown below. Upon processing, thePOS device 110 may then send an optical and/or audible transactionstatus message to the RFID reader 104 (step 830) for communication tothe customer (step 832).

The methods for processing the transactions may include one of severalformats as required by the fob issuer. For example, one processingmethod may include processing the transaction under a preloaded fobformat wherein a payment value (e.g., monetary value, reward pointsvalue, barter points value, etc.) may be preloaded into an preloadedvalue account or data file prior to permitting usage of the fob. In thisway, the user may be permitted to set aside a payment amount fortransactions for goods and services using the fob. During processing ofthe transaction, approval of the transaction may involve comparing thetransaction amount to the amount stored (or remaining) in the preloadedvalue data file. Comparison may be made by a preloaded value processingsystem wherein the preloaded value processing system may compare thetransaction amount to be processed to the preload value data file. Wherethe transaction amount exceeds the amount stored in the preloaded valueaccount, the preloaded value processing system may deny authorizationfor completion of the transaction. Contrarily, where the transactionamount does not exceed the amount stored in the preloaded value datafile account the preloaded value processing system may provide forauthorization of the transaction.

An exemplary preloaded value processing system 1000 is shown withrespect to FIG. 10. Preloaded value processing system 1000 may include afob 102 including a transponder 114, which is in communication with amerchant system 130 via an RFID reader 104 or a computer interface 134as is described with respect to FIG. 1A. The merchant system may be incommunication with an issuer system 1010, where the issuer system 1010may be maintained by any entity (e.g., financial institution, AmericanExpress, Visa and/or MasterCard, etc.) which permits the fob 102 user tostore a preload value in a preloaded value account (e.g., data file)maintained on an issuer database 1012 of similar construction asdatabase 212. The issuer system 1000 may further include one or moreprocess servers for processing a fob transaction. As shown, a POS device110 (included in merchant system 130) may be in communication with anissuer account server (IAS) 1014 for receiving the fob accountinformation from POS device 110. IAS 1014 may be in furthercommunication with a preloaded value authorization server (PLAS) 1016for processing transactions involving a preloaded value fob. The PLAS1016 may be in further communication with an issuer database 1012 forretrieving funds from the preloaded value data file (not shown) whichare necessary for satisfying the preloaded fob or merchant transactionrequest.

As used herein, the term “issuer” or “account provider” may refer to anyentity facilitating payment of a transaction using a fob, and whichincluded systems permitting payment using at least one of a preloadedand non-preloaded fob. Typical issuers maybe American Express,MasterCard, Visa, Discover, and the like. In the preloaded valueprocessing context, an exchange value (e.g., money, rewards points,barter points, etc.) may be stored in a preloaded value data file foruse in completing a requested transaction. The exchange value may not bestored on the fob itself. Further, the preloaded value data file may bedebited the amount of the transaction requiring the preloaded value datafile to be replenished. As described more fully below, the preloadedvalue system platform may be used to complete “direct link”transactions. In which case, the preloaded value account may function asa place holder, perpetually storing a zero value.

The preloaded value data file may be any conventional data fileconfiguration for storing a value (e.g., monetary, rewards points,barter points, etc.) which may be exchanged for goods or services. Inthat regard, the preloaded value data file may have any configuration asdetermined by the issuer system 1010.

In exemplary operation, a fob identifying information (e.g., accountnumber or fob marker) may be provided to the POS device 110 in similarmanner as was discussed with respect to FIG. 1A. That is, the fob 102may be presented to the merchant system 130 via an RFID reader 104 or acomputer interface 134, which may provide the fob identifyinginformation in Track 1 or Track 2 format. A POS device 110 included inthe merchant system 130 may receive the fob 102 identifying informationand provide the fob 102 identifying information along with thetransaction identifying information (e.g., amount, quantity, merchantidentification, etc.) to the issuer system 1010 for authorization. Themerchant system 130 may additionally include a merchant system marker oridentifier for indicating a merchant system identity. The merchantsystem 130 may combine the fob 102 identifying information, the merchantidentifying information, or the transaction identifying information, orany combination thereof, into a merchant transaction request forproviding to the issuer system 1010.

The IAS 1014 may receive the transaction and fob identifying information(or merchant transaction request) and recognize that the transaction isbeing requested relative to a preloaded value account associated with apreloaded fob. That is, the IAS 1014 may recognize that the user haspresented a preloaded fob 102 for payment. Recognition of the fob 102 asa preloaded fob may mean that the fob identifying information includes amarker or identifier indicating that the fob is associated with apreloaded value data file. Upon recognition of the marker, the IAS 1014may forward transaction and fob identifying information to the PLAS 1016for processing. PLAS 1016 may compare the transaction amount to thevalue stored or remaining in the preloaded value to determine ifauthorization should be granted or denied. Where the transaction amountexceeds the value stored in the preloaded value data file the PLAS 1016may forward a transaction denied message to the IAS 1014 for providingto the merchant system 130. Alternatively, where the transaction amountis less than or equal to the value stored in the preload value data filethe PLAS 1016 may deduct from the preloaded value data file thenecessary amount for satisfaction of the transaction.

As noted above, in one exemplary embodiment of the present invention,the PLAS 1016 may provide a transaction denied message to the IAS 1014where the amount stored in the preloaded value account is less thanrequired for satisfying the merchant or fob transaction request. In thisinstance, where the preloaded value falls below a predetermined minimumlevel (e.g., minimum depletion level), it may be necessary for the fobuser to reload the preloaded value data file. Reloading of the preloadedvalue account may take place manually (e.g., by the fob usertelephonically or online) or may take place automatically when the valuestored in the preloaded value data file is depleted to a predefinedlevel. Where the reloading is done automatically, reloading may occurunder rules established by the fob issuer or owner. For example,reloading may occur at preselected time limits, when the reserve isbelow a predetermined amount, until a maximum number of reloads in apredetermined time period has occurred or until a maximum reload amountis reached in a predetermined time period.

FIG. 11A depicts an exemplary preloading and reloading processes whichmay be performed in accordance with the present invention. Thepreloading and reloading processes may be performed using one or moreservers (e.g., PLAS 1016) in communication with a funding source 1104.Although the processes are demonstrated using a PLAS 1016, it iscontemplated that any server for establishing and managing data filesmay be used. However, to facilitate further understanding of theinvention, the preloading and reloading aspects of the invention aredescribed with reference to PLAS 1016.

PLAS 1016 may be used to establish on the server or on a database (e.g.,database 1012) a preloaded value account (e.g., data file) (1106). Thepreload value account may be funded or maintained by a fob issuer whichmay establish a credit, charge, debit, rewards value account, etc. inconnection with a charge or credit card (e.g., Visa, MasterCard,American Express, Discover, etc.), debit or direct debit authorization(DDA) system.

The preloaded value account may be established to at least apredetermined minimum preload amount or value (e.g., minimum preloadlevel) as determined by the account provider and/or the fob user orowner. In this context, the predetermined minimum value (e.g., minimumpreload value) required to establish the preloaded value account mayvary with respect to a particular fob user. The preloaded value accountmay be loaded (e.g., preloaded or reloaded) from funds received from oneof a funding source account 1104 (American Express, Visa, MasterCard,Discover, etc.). That is, the PLAS 1016 may communicate with the fundingsource 1104 to obtain funds or value for loading or reloading thepreloaded value account (1108).

FIG. 11B shows an exemplary reloading process in accordance with theinvention. During operation, a consumer may present to a merchant system130 the prepaid fob 102 for purchasing goods or services (1110). Thepreloaded value account is then depleted the value amount paid to themerchant system 130. The process for purchasing goods may be repeateduntil the value stored in the preloaded value account equals or is lessthan a minimum level balance (e.g., minimum depletion level). Theminimum depletion level may be predetermined by the fob user or fobissuer, and may be the minimum value permitted to be stored in thepreloaded value account before the file is to be reloaded.

Once the preloaded value data is depleted such that the minimumdepletion level is reached, the PLAS 1016 may trigger an automaticreload to reload the preloaded value account from funds retrieved fromthe funding source 1104 (1112). The amount of funds retrieved may besufficient for loading the preloaded value account to the minimum amountdescribed above or to some other predetermined reload value. In oneexemplary embodiment, the PLAS 1016 may trigger automatic reloadingwhere a predetermined minimum depletion level (e.g., “minimum levelbalance”) is reached. That is, the preloaded value account may not beentirely depleted to zero value before automatic reloading occurs. Inthis instance, the PLAS 1016 may charge the funding necessary forautomatic reloading against the available funds at funding source 1104.In another exemplary embodiment the automatic reloading may occur wherethe transaction exceeds the amount stored in or remaining in thepreloaded value account. In this way, the preloaded value account may berestored to an amount necessary for completion of the transaction. Forexample, where automatic reloading restores the preloaded value accountto a value suitable for transaction completion, the preloaded valueaccount may be automatically reloaded prior to processing thetransaction.

In another exemplary embodiment, automatic reloading may occur based ondifferent user or issuer automatic reload criteria. Other automaticreload criteria may include, but are not limited to, reloading until adefined maximum load amount in a defined time period is reached,reloading at a selected reoccurring time interval (e.g., once a month),reloading as permitted until a defined maximum number of reloads in aspecified time period is reached, or reloading until a defined maximumreload amount is reached in a specified time period, etc. In someinstances, reloading may be done manually, such as, for example, whenthe fob user contacts the issuer telephonically or via user interface toprovide a specified funding criteria for use in reloading the preloadedvalue account.

In yet another exemplary embodiment, the preloaded value transactionprocessing system may permit approval of a transaction where thetransaction value exceeds the preloaded value amount stored in thepreloaded value account. That is, the preloaded fob may be used forpurchases exceeding the preloaded value amount provided that the chargesubmitted by the merchant is less than or equal to the maximum reloadamount permitted plus the amount stored on the card at the time thecharge is submitted.

In another exemplary embodiment, the preloaded value system may approvetransactions based on a particular merchants transaction processingprotocol. Where the issuer has reviewed and/or approved a merchant'stransaction processing method, the system may take the method inconsideration in determining whether to approve a merchant's transactionrequest. For example, a merchant's transaction processing method mayinclude the merchant submitting transaction requests which exceed thepreloaded value amount, but the actual charge may be less than or equalto the preloaded value amount. Under this transaction processing methoda merchant, such as, for example, a gasoline merchant, may seekpre-approval of an anticipated gasoline fueling amount. Neither theconsumer nor the merchant may know the final value of the purchase,especially, for example, where the consumer decides to fill hisautomobile gas tank or purchase non-fuel items. Thus, the merchant maysubmit a transaction request which may be higher than the final amountof the transaction. In this instance, the preloaded value transactionprocessing system may still be configured to approve the transactionrequest. The processing system may recognize that a transaction camefrom a particular merchant and institute a predetermined approvalprotocol correlative to that merchant, since the approval protocol mayinclude information that the merchant is sending a transaction requestexceeding the actual charge.

The transaction processing system may use any one of the acceptabletechniques for identifying merchants, such as recognition of themerchant ID, or a marker appended to the transaction, etc. Theprocessing system may correlate the merchant ID with a merchant protocolfor requesting a transaction approval of an amount greater than thepreloaded value (or reload value), and approve the merchant requestaccordingly.

In accordance with an alternate exemplary embodiment of a preloadedvalue processing system 1000, upon receiving the transaction requestfrom the IAS 1014, the PLAS 1016 may evaluate the transaction requestbased upon several risk criteria established by the issuer. If all thecriteria are successfully met, then the PLAS 1016 may send authorizationof the transaction (e.g., “transaction granted”) to the IAS 1014 forproviding to the merchant system 130. Simultaneous with or subsequentto, providing the transaction authorization to the IAS 1014, the PLAS1016 may seek satisfaction of the transaction from the fob value accountmaintained on the account provider database 1012. The transactionrequest may be provided to the IAS 1014 for processing. That is, the IAS1014 may seek to deduct the transaction value from the balance of theamount stored in the preloaded value account.

FIG. 12 depicts an exemplary embodiment of another transactionprocessing system (“direct link” system) 1200 in accordance with thepresent invention. More particularly, FIG. 12 depicts a direct linksystem 1200 which may be used to process a merchant transaction request.In this context, a direct link system may be any system whichfacilitates satisfaction of a transaction request using a fob or otherpresentable medium (credit card, charge card, debit card, etc.) directlylinked to an account which stores an exchange value (e.g., money, creditor charge, or rewards points, etc.). In this instance, the preloadedvalue account may not be preloaded as described above. Further, thepreloaded value account may be linked to a contact product such as acredit, debit, and/or DDA card, and the like, which may be presented forpayment of goods and services. In this regard, the fob (here called“direct link fob”) and the card are associated with the same fundingsource and the user or merchant may seek satisfaction of a transactionfrom the funding source independent of whether the direct link fob orcard is used.

In the exemplary direct link system 1200, the direct link fob 102 usermay not establish a preloaded value account with value. Instead, thepreloaded value account may perpetually store a zero value or the fob102 may be associated with a fob transaction account which may be usedto provide payment to the merchant for goods and services where theaccount may be a credit, debit, loyalty account or the like.

In accordance with an exemplary embodiment of the invention, atransaction request associated with a direct link fob 102 may beprocessed using the preloaded value transaction system processingdescribed above. However, as noted, in this instance the preloaded valueaccount is used as a place holder storing a zero value. A transactionaccount containing a transaction account value which is associated withthe direct link fob is treated as the funding source for satisfyingdirect link transactions. In this instance, the transaction may besatisfied according to a fob user or issuer predefined protocol orcriteria.

As shown, the merchant system 130 may be in communication with an issuersystem 1010 for receiving a merchant transaction request. Moreparticularly, the POS device 110 may be in communication with an issuerserver, such as, for example, an issuer account server (IAS) 1014 forreceiving the merchant and/or transaction identifying information. IAS1014 may be in further communication with a PLAS 1016 for processing themerchant transaction request. In some instances the PLAS 1016 may be infurther communication with a second IAS 1202, although a second IAS 1202may not be required where one or more of the existing servers mayperform the functions of IAS 1202 described below. However, the IAS 1202is included herein to simplify the understanding the operation of thisexemplary embodiment.

In exemplary operation of system 1200, the direct link fob identifyinginformation (e.g., fob identifier or account number) may be provided tothe POS device 110 in similar manner as was discussed with respect toFIG. 1A. That is, the direct link fob 102 may be presented to themerchant system 130 via an RFID reader 104 or a computer interface 134,which may provide the direct link fob 102 identifying information inTrack 1 or Track 2 format. A POS device 110 included in the merchantsystem 130 may receive the direct link fob 102 identifying informationand provide the direct link fob 102 identifying information along withthe transaction identifying information (e.g., amount, quantity,merchant identification, etc.) to the issuer system 1010 forauthorization.

The IAS 1014 may receive the transaction and fob identifying informationand recognize that the transaction as being requested relative to adirect link fob 102. Recognition of the direct link fob 102 in thisinstance may mean that the direct link fob 102 identifying informationincludes a marker or identifier indicating that the fob is associatedwith a zero value preloaded value account. Upon recognition of themarker, the IAS 1014 may forward the transaction and fob identifyinginformation to PLAS 1016 for processing.

In similar manner as was described with respect to the operation of thepreloaded value processing system of FIG. 10, the PLAS 1016 may evaluatethe transaction request based upon several risk criteria established bythe issuer. Exemplary risk criteria may include, but are not limited to,consideration of transaction amount limits for a specified time period,fob user usage history, fund or reserve limits, pre-determinedre-funding rules, user defined limits, etc. If all the criteria aresuccessfully met, then the PLAS 1016 may send authorization of thetransaction (e.g., “transaction granted”) to the IAS 1014 for providingto the merchant system 130. The transaction authorization may beprovided to the merchant system 130 based on evaluation of the riskcriteria and not upon the value present in preloaded value account ordirect link transaction account storing value relative to the directlink fob.

After providing the transaction authorization to the IAS 1014, the PLAS1016 may seek authorization of the transaction against the direct linkfob account (e.g., transaction account) which is maintained on theissuer database 1012, and which is funded by value received from afunding source 1104. The authorization request may be provided to theIAS 1202 for approval which may retrieve the necessary value from thedirect link fob account. For example, where the direct link fob accountis a charge or credit account, the PLAS 1016 may request authorizationfrom the second IAS 1202 and the IAS 1202 may assess the transactionamount against the direct link fob account on database 1012. The IAS1202 may seek to record the amount of the transaction in the direct linkfob usage history data file for payment at the end of a billing cycle(e.g., charge account), or the amount may be recorded on the fob directlink fob usage data file for payment at a date later than the end of thebilling cycle (e.g., credit account).

In an alternative operation the PLAS 1016 may assess the transactionamount against the direct link fob account, without use of a second IAS1202. Whether the transaction is processed using a second IAS 1202, itis to be understood that value may not be immediately transferred to themerchant system from the direct link fob account for satisfying thetransaction. Instead, the direct link fob issuer guarantees satisfactionof the merchant transaction request until the necessary value isretrieved from the direct link fob account at the end of the billingcycle or later.

In yet another exemplary transaction processing system 1300 depicted inFIG. 13, the merchant system 130 may provide a batch file containingmultiple fob transaction requests to be processed to a process server1302 where the multiple fob transactions may include both preloadedvalue and direct link transaction request. The system 1300 may include aprocess server 1302 which distinguished between preloaded value anddirect link transaction requests. That is, process server 1302 may beused for separating the fob transactions which are associated with apreloaded fob account and those that are not associated with a preloadedfob account, as discussed more fully below. The process server 1302 mayfurther be in communication with an IAS 1014 for seeking settlement ofthe transaction. The IAS 1014 may process the transaction request inaccordance with the direct link transaction process or the preloadedvalue transaction platform described above.

In exemplary operation of system 1300, the process server 1302 mayreceive the settlement file and create sub-files of transaction requestsrelative to the type of fob used in the transaction (e.g., preloadedfob, and direct link fob associated with a charge or credit account).The process server 1302 may create a first fob transaction file formerchant payables and a second fob transaction file for accountsreceivable to be forwarded to the IAS 1014 for processing. Where thesub-file includes merchant payable, the process server 1302 may providefunds to the merchant for payment of the transaction, where the fundsprovided may be equivalent to the transaction amount minus discountrevenues. The funds may be retrieved from the funding source forproviding to the merchant. Alternatively, the process server 1302 maycreate a second fob transaction file for accounts receivable paymentsand forwarded the second fob transaction file to the IAS 1014. IAS 1014may then process the transaction request according to the processesdescribed in FIGS. 10 and 12. That is, the IAS 1014 may distinguish thepreloaded fob transaction requests from those associated with the directlink fob and process the transactions accordingly.

Considering the operation of the various transaction processing systemsdescribed above, it can be seen that the transaction processing systemsdescribed may distinguish when a preloaded fob is used, when a cardassociated with a fob is used, or when an account associated with apreloaded fob is reloaded. In that regard, the present invention may beused to reward points depending on the nature of the fob usage. Thepoints (e.g., loyalty points) may be stored in a points or rewardsaccount maintained on the issuer database (e.g., database 1012). Therewards points may then later be redeemed from the rewards account forexchange for goods and services as desired by the fob user.

As noted, in one instance, points may be provided when the fob is usedas opposed to when the card associated with the fob is used. Forexample, the IAS 1014 may recognize that a fob is being used and awardpoints (e.g., loyalty points) to the rewards account assigned to the fobuser or associated with the fob. The loyalty points may be awarded basedon any criteria as determined by the fob issuer. Exemplary rewardingcriteria may include rewarding points for, for example, frequency of fobusage, amount of individual purchase using the fob, or the total amountof purchases in a given time period.

Where the fob is associated with a preloaded value account such as thatdescribed with respect to FIG. 10, points may be awarded for accountreloading. That is, IAS 1014 may place award points in the rewardsaccount relative to the amount loaded or reloaded as required. Furtherthe IAS 1014 may place reward points in the rewards account relative tousage of the fob at a particular merchant or for a particulartransaction.

It should be noted that the transaction account associated with the fob102 may include a usage restriction, such as, for example, a perpurchase spending limit, a time of day use, a day of week use, certainmerchant use and/or the like, wherein an additional verification isrequired when using the fob outside of the restriction. The restrictionsmay be personally assigned by the fob 102 user, or the account provider.For example, in one exemplary embodiment, the account may be establishedsuch that purchases above $X (i.e., the spending limit) must be verifiedby the customer. Such verification may be provided using a suitablepersonal identification number (PIN) which may be recognized by the RFIDreader 104 or a payment authorization center (not shown) as being uniqueto the fob 102 holder (e.g., customer) and the correlative fob 102transaction account number. Where the requested purchase is above theestablished per purchase spending limit, the customer may be required toprovide, for example, a PIN, biometric sample and/or similar secondaryverification to complete the transaction.

Where a verification PIN is used as secondary verification theverification PIN may be checked for accuracy against a corroborating PINwhich correlates to the fob 102 transaction account number. Thecorroborating PIN may be stored locally (e.g., on the fob 102, or on theRFID reader 104) or may be stored on a database (not shown) at thepayment authorization center. The payment authorization center databasemay be any database maintained and operated by the fob 102 transactionaccount provider.

The verification PIN may be provided to the POS device 110 using aconventional merchant (e.g., POS) PIN key pad 118 in communication withthe POS device 110 as shown in FIG. 1, or an RFID keypad incommunication with the RFID reader 104. PIN keypad may be incommunication with the POS device 110 (or alternatively, RFID reader104) using any conventional data link described above. Upon receivingthe verification PIN, the RFID reader 104 may seek to match the PIN tothe corroborating PIN stored on the RFID reader 104 at database 310 or320. Alternatively, the verification PIN may be provided to a paymentauthorization center to determine whether the PIN matches the PIN storedon the payment authorization center database which correlates to the fob102 account. If a match is made, the purchase may no longer berestricted, and the transaction may be allowed to be completed.

In an alternate embodiment, verification of purchases exceeding theestablished spending limit may involve biometrics circuitry included infob 102. FIG. 9 is a schematic block diagram of an exemplary fob 102wherein fob 102 includes a biometric security system 902. Biometricsecurity system 902 may include a biometric sensor 904 for sensing thefingerprint of the fob 102 user. The biometric sensor 902 may be incommunication with a sensor interface/driver 906 for receiving thesensor fingerprint and activating the operation of fob 102. Incommunication with the biometric sensor 904 and sensor interface 906 maybe a battery 903 for providing the necessary power for operation of thebiometric security system components.

In one exemplary application of the fob 102 including the biometricsecurity system 902, the customer may place his finger on the biometricsensor to initiate the mutual authentication process between the fob 102and the RFID reader 104, or to provide secondary verification of theuser's identity. The sensor fingerprint may be digitized and comparedagainst a digitized fingerprint stored in a database (e.g., securitydatabase 212) included on fob 102. Such comparison step may becontrolled by protocol/sequence controller 208 and may be validated byauthentication circuit 210. Where such verification is made, the mutualauthentication between fob 102 and RFID reader 104 may begin, and thetransaction may proceed accordingly. Alternatively, the comparison maybe made with a digitized fingerprint stored on a database maintained bythe fob 102 transaction account provider system (not shown). Thedigitized fingerprint may be verified in much the same way as isdescribed above with respect to the PIN.

In one exemplary application of the fob 102 including the biometricsecurity system 902, the system 902 may be used to authorize a purchaseexceeding the established per purchase spending limit. In this case,where the customer's intended purchase exceeds the spending limit, thecustomer may be asked to provide assurance that the purchase isauthorized. Accordingly, the customer may provide such verification byplacing his finger over the biometric sensor 904. The biometric sensor904 may then digitize the fingerprint and provide the digitizedfingerprint for verification as described above. Once verified, fob 102may provide a transaction authorized signal to RF transponder 202 (oralternatively to transponder 220) for forwarding to RFID reader 104.RFID reader 104 may then provide the transaction authorized signal tothe POS device 110 in similar manner as is done with convention PINdriven systems and the POS device 110 may process the transaction underthe merchant's business as usual standard.

In accordance with another exemplary embodiment of the invention, thefob user is provided limited access to a fob user data file maintainedon an issuer system for managing the fob usage and fob user information.The fob user may access the fob user data file to change, for example,demographic information (e.g., fob user address, phone number, emailaddress, etc.), the funding source (e.g., credit account, chargeaccount, rewards account, barter account, etc.) associated with the fob,view the transaction history, etc. In addition, the fob user may bepermitted to load or reload the account or alter automatic reloadparameters (e.g., amount to reload, period for reloading, etc.).

With reference to FIG. 1A, the fob user may connect the fob 102 to acomputer interface 134 via the USB interface 132. The fob user may thenuse the computer interface 134 to access the fob user data file via thenetwork 136. In particular, the network 136 may be in communication withan issuer system (e.g. system 1010 of FIG. 10) and may be providedlimited access to an issuer server (e.g., server 1014) for managing thefob. The issuer server 1014 may be in communication with an issuersystem database (e.g., 1012) which stores the information to be managedrelative to the user fob user data file. The changes made to the fobuser data file by the fob user may be made in real-time, after a briefdelay, or after an extended delay. In one instance, changes may bestored in a batch changes file on the issuer database for later batchprocessing.

The fob user may be provided limited access to all or a portion of theissuer system 1010 to define a funding protocol for use in satisfying atransaction request. The fob user may be permitted access to all or aportion of the issuer database 1012 for defining the protocol fordetermining the funding source to be used for a particular transaction.The user may contact the provider or any other third party that canfacilitate changing the funding source via any means known in the artsuch as, for example, telephone, voice response, internet, cell phone,modem, email, webpage submission and/or any other electronic, optical ordigital methods for communication. The fob user may be permitted toselect one or more particular funding source for use with the fobdepending on the conditions of the transaction request. For example, thefunding protocol may indicate to the issuer (e.g., account provider)server (e.g. IAS 1014) that a particular funding source is to be usedfor an identified class of transactions or for a particular merchant.The funding protocol may take into account the requirements asdetermined by a particular funding source, or the relative risk level(e.g., high risk, medium risk, low risk, or the like) in determiningwhich funding source or combination of sources are to be used to satisfya transaction request. Alternatively, the funding protocol may indicatethat a combination of sources may be used to satisfy a transactionrequest. In this arrangement, the primary, secondary, tertiary fundingsources may have similar descriptions as any one of funding sources 1104described above. In this regard, the database 1012 may include sub-datafiles corresponding to one or more funding sources, where the sub-datafiles may funded from value received from the multiple funding sources.For example, a primary sub-data file may include value received from aprimary funding source and a secondary sub-data file may include valuereceived from a secondary funding source. Alternatively, the inventionmay include multiple databases (not shown) for uniquely storing thefunds received from, for example, a primary and secondary fundingsource. Further, although the invention is described with respect toprimary and secondary funding source, it is to be understood that anynumber n of funding sources for providing value to n sub-data files iscontemplated, and that the terms primary and secondary are used hereinby way of example. In one exemplary embodiment, where multiple fundingsources are used to satisfy a transaction, the invention may requireauthentication from one or more of the funding sources that thetransaction is authorized. Thus, an authorization may take place uponpresentment of the fob 102 and when the value is retrieved from afunding source (or multiple funding sources) to complete a transaction.

FIG. 14 depicts an exemplary funding protocol 1400 which may beidentified by the fob user. As shown, the funding protocol may beinitiated when the fob 102 is presented for payment (step 1402). The fob102 may be presented to an RFID reader 104. The RFID reader 104 or thecomputer interface 134 may provide an account number to the merchantsystem 130 and the merchant system 130 may seek satisfaction of atransaction request from an issuer system 1010 (step 1404).

The fob 102 user may indicate via the database 1012 that a particularmerchant or class of transactions is to be flagged or marked forsatisfaction using a particular funding source. The merchant or class oftransactions may be flagged in similar manner as is discussed above.That is, the fob user defined protocol may provide for a particularmerchant, type of merchant, or class of transactions to be marked andidentified by the account provider for specified treatment, as describedmore fully below.

If a merchant (or transaction) is flagged, the issuer server 1014 mayswitch the funding source associated with the fob 102 from a primaryfunding source to a secondary funding source (step 1408). In thisregard, the server may retrieve value from the sub-data file associatedwith the secondary funding source. The server 1014 may additionallydetermine whether the spending limit for the secondary funding sourcehas been reached or exceeded (step 1410). If the spending limit for thesecondary funding sources is not exceeded, then the server may retrievethe appropriate value for satisfying a transaction request from thesecondary funding source (step 1414). The funds may then be transferredto the merchant system 130 under any business as usual standard (step1416), completing the merchant's transaction request.

In some instances, the funding may be switched from the primary fundingsource to the secondary funding source (step 1408), and the spendinglimit for the secondary funding source is reached or exceeded (step1410). In which case, the issuer server 1014 may determine whether thefob user has indicated that the merchant transaction request is to besatisfied using funds retrieved from a combination of funds receivedfrom the sub-data files associated with the primary and secondaryfunding sources (step 1412). The combination of funds may be retrievedusing any formula determined by the fob user or fob account issuer (step1430), and the funds may be transferred to the merchant system 1014,satisfying the merchant transaction request.

In another embodiment, the server may determine if a switch is to bemade to yet a tertiary funding source (step 1432). In which case, theserver may determine if the spending limit for the tertiary fundingsource has been reached or exceeded (step 1436). If the funds areexceeded, the merchant request may be terminated and a “transactiondenied” message may be forwarded to the merchant system 130 (step 1434).

Where a merchant transaction request is not flagged (step 1406), in oneembodiment, the issuer server 1014 may not switch from a primary fundingsource to a secondary funding source. Instead, the issuer server 1014may determine whether the spending limit on the primary source isreached or exceeded (step 1420). If the spending limit on the primarysource is not exceeded, then the appropriate funds for satisfying themerchant request may be retrieved from the primary funding sourcesub-data file (step 1422) and transferred to the merchant system 130under business as usual standards (step 1424).

Contrarily, where the spending limit on the primary funding source isreached or exceeded (step 1420), in one embodiment, the issuer server1014 may determine whether to combine funds retrieved from sub-datafiles associated with the primary funding source and a secondary fundingsource to satisfy the merchant transaction request (step 1426). If theprimary and secondary funding sources are to be combined, funds may beretrieved from the multiple funding sub-data files using any formula asdetermined by the fob user or fob account issuer (step 1430). The fundsmay then be transferred to the merchant system 130 under business asusual standards (step 1424).

If the funds from the primary and secondary funding sources are not tobe combined, the server may determine whether to switch from a primaryfunding source to a secondary funding source (step 1428). If no switchis to be made and the transaction request exceeds the primary fundingsource limit, then the transaction request may be terminated and a“transaction denied” may be provided to the merchant under business asusual standards (step 1434).

On the other hand, should the funding source be switched from a primaryfunding source to a secondary funding source, the server 1014 maydetermine whether the spending limit for the secondary funding source isreached or exceeded (step 1440). If the spending limit for the secondaryfunding source is reached or exceeded, then the transaction may beterminated and a “transaction denied” message may be provided to themerchant system 130 under business as usual standards (step 1434). Ifthe spending limit for the secondary funding source is not reached orexceeded, the appropriate funds for satisfying the transaction requestmay be retrieved from the sub-data file associated with the secondaryfunding source (step 1442) and transferred to the merchant system 130(step 1424), satisfying the transaction request.

The preceding detailed description of exemplary embodiments of theinvention makes reference to the accompanying drawings, which show theexemplary embodiment by way of illustration. While these exemplaryembodiments are described in sufficient detail to enable those skilledin the art to practice the invention, it should be understood that otherembodiments may be realized and that logical and mechanical changes maybe made without departing from the spirit and scope of the invention.For example, the steps recited in any of the method or process claimsmay be executed in any order and are not limited to the order presented.Further, the present invention may be practiced using one or moreservers, as necessary. Thus, the preceding detailed description ispresented for purposes of illustration only and not of limitation, andthe scope of the invention is defined by the preceding description, andwith respect to the attached claims.

What is claimed is:
 1. A method, comprising: receiving, at a paymentprocessor, a request for a transaction, the request including a codefrom a radio frequency (RF) transponder device; verifying, by thepayment processor, the RF transponder device; authorizing, by thepayment processor, use of a first funding source according to a fundingaccount protocol associated with the code; funding, by the paymentprocessor, the transaction with the first funding source according tothe funding account protocol; authorizing, by the payment processor, useof a second funding source according to the funding account protocol;and changing, by the payment processor, the funding of the transactionfrom the first funding source to the second funding source according tothe funding account protocol in response to an amount of the transactionexceeding an available value of the first funding source.
 2. The methodof claim 1, wherein the funding account protocol includes apredetermined formula.
 3. The method of claim 1, wherein the fundingaccount protocol involves the first funding source and the secondfunding source.
 4. The method of claim 1, further comprising receivingfunds from the second funding source in response to a first fundingsource value associated with the first funding source being less than aminimum depletion value associated with the first funding source.
 5. Themethod of claim 1, further comprising receiving funds from at least oneof the first funding source or the second funding source according to aformula determined at least partially by at least one of: a merchantsystem, a payment processor system, an RF reader, a transactionprocessing system, a transponder device user, the RF transponder device,a loyalty points system, a first funding source system, or a secondfunding source system.
 6. The method of claim 1, further comprisingreceiving funds from at least one of the first funding source or thesecond funding source in accordance with at least one of: an amountassociated with the transaction, a merchant type associated with thetransaction, a first funding source value, a second funding sourcevalue, or a date of the request.
 7. The method of claim 1, wherein thefunding account protocol is stored on at least one of: a merchantsystem, a payment processor system, an RF reader, the RF transponderdevice, a transaction processing system, a first funding source system,or a second funding source system.
 8. The method of claim 1, furthercomprising receiving a predetermined combination of funds from the firstfunding source and the second funding source in response to the amountof the transaction exceeding the available value of the first fundingsource.
 9. The method of claim 8, wherein the predetermined combinationof funds comprises a percentage of a value of the transaction from thefirst funding source and a balance of the value of the transaction fromthe second funding source.
 10. The method of claim 1, wherein thetransaction is funded by the second funding source in response to theamount of the transaction exceeding the available value of the firstfunding source.
 11. A non-transitory computer readable medium havinginstructions stored thereon that, in response to execution by a paymentprocessor, causes the payment processor to perform operationscomprising: receiving a request for a transaction, the request includinga code from a radio frequency (RF) transponder device; verifying the RFtransponder device; authorizing use of a first funding source accordingto a funding account protocol associated with the code; funding thetransaction with the first funding source according to the fundingaccount protocol; authorizing use of a second funding source accordingto the funding account protocol; and changing the funding of thetransaction from the first funding source to the second funding sourceaccording to the funding account protocol in response to an amount ofthe transaction exceeding an available value of the first fundingsource.
 12. The non-transitory computer readable medium of claim 11,wherein the funding account protocol includes a predetermined formula.13. The non-transitory computer readable medium of claim 11, wherein thefunding account protocol involves the first funding source and thesecond funding source.
 14. The non-transitory computer readable mediumof claim 11, further comprising receiving funds from the second fundingsource in response to a first funding source value associated with thefirst funding source being less than a minimum depletion valueassociated with the first funding source.
 15. The non-transitorycomputer readable medium of claim 11, further comprising receiving fundsfrom at least one of the first funding source or the second fundingsource according to a formula determined at least partially by at leastone of: a merchant system, a payment processor system, an RF reader, atransaction processing system, a transponder device user, the RFtransponder device, a loyalty points system, a first funding sourcesystem, or a second funding source system.
 16. The non-transitorycomputer readable medium of claim 11, further comprising receiving fundsfrom at least one of the first funding source or the second fundingsource in accordance with at least one of: an amount associated with thetransaction, a merchant type associated with the transaction, a firstfunding source value, a second funding source value, or a date of therequest.
 17. The non-transitory computer readable medium of claim 11,wherein the funding account protocol is stored on at least one of: amerchant system, a payment processor system, an RF reader, the RFtransponder device, a transaction processing system, a first fundingsource system, or a second funding source system.
 18. An apparatus,comprising: a payment processor configured to: receive a request for atransaction, the request including a code from a radio frequency (RF)transponder device; verify the RF transponder device; authorize use of afirst funding source according to a funding account protocol associatedwith the code; fund the transaction with the first funding sourceaccording to the funding account protocol; authorize use of a secondfunding source according to the funding account protocol; and change thefunding of the transaction from the first funding source to the secondfunding source according to the funding account protocol in response toan amount of the transaction exceeding an available value of the firstfunding source.